Skip to content

Remove Safe checks - #33

Open
JAG-UK wants to merge 1 commit into
filecoin-project:mainfrom
JAG-UK:fix/remove-safe-check
Open

Remove Safe checks#33
JAG-UK wants to merge 1 commit into
filecoin-project:mainfrom
JAG-UK:fix/remove-safe-check

Conversation

@JAG-UK

@JAG-UK JAG-UK commented Aug 25, 2026

Copy link
Copy Markdown

In response to issue #30 this PR removes the Safe check entirely. This reduces testing burden and smart contract weight but does leave a lot of avenues for user error and unrecoverable situations in these important accounts.

@JAG-UK

JAG-UK commented Aug 25, 2026

Copy link
Copy Markdown
Author

Note this is an alternative to #32 - we can only merge one of these!

@FilOzzy FilOzzy moved this from 📌 Triage to 🔎 Awaiting review in FOC Aug 25, 2026
@BigLep BigLep moved this from Backlog to In review in Solstice Aug 25, 2026
@BigLep
BigLep requested a review from wjmelements August 25, 2026 15:59
Comment thread src/StreamWeightActor.sol
Comment on lines -35 to -37
owner1.isProbablyASafe();
owner2.isProbablyASafe();

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we go with this approach, I still want to verify that the owners are contracts. like address.code.length > 0

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds reasonable. Maybe if we land there I could update #32 instead of this one, and put in address.code.length > 0 in addition to or even instead of the multisig owner count calls.

Just because all the check plumbing is still there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

4 participants